| 1. |
Jeeves—Thriving Organically as a Humble Servant ( Pages)
by P.J. Jakovljevic
Apr 17, 2006
Abstract : Jeeves Information Systems, an innovative Swedish enterprise applications provider, seems to be making the right moves towards remaining a force within its markets. But becoming a more globally recognized player remains a tall order, even for an obliging butler-like vendor.
|
| 2. |
Competition from a Small Vendor ( Pages)
by P.J. Jakovljevic
Mar 29, 2006
Abstract : One reason to look at small specialist providers is the ongoing success of Sweden-based Jeeves Information Systems AB. Even the largest players acknowledge the challenges and the driving forces coming from the focused and innovative likes of Jeeves.
|
| 3. |
Attaining Real Time, On-demand Information Data: Contemporary Business Intelligence Tools ( Pages)
by Olin Thompson & P.J. Jakovljevic
Jun 29, 2005
Abstract : Demand for instant access to dispersed information is being met by vendors offering enterprise business intelligence tools and suites. Portlet standardization, enterprise information integration, and corporate performance management are among the proposed solutions, but do they really deliver real time information?
|
| 4. |
Information Technology (IT) - IT Acronym Definition and Related White Papers ( Pages)
by TEC Staff
Jun 13, 2009
Abstract : Information technology (IT) is the study, design, development, implementation, support or management of computer-based information systems, particularly software applications and computer hardware (source: Information Technology Association of America [ITAA]).
|
| 5. |
Manual versus Information Technology Enabled Lean Manufacturing ( Pages)
by P.J. Jakovljevic
Feb 16, 2006
Abstract : All good lean systems have both physical systems in the plant and near real time information technology backbones that centralize data. The primary advantage of enterprise systems is that they can handle considerably more information than can be accommodated manually.
|
| 6. |
Architecture-Centered Information Systems In The Manufacturing Domain - Part II - The Architecture Process ( Pages)
by Glen B. Alleman
Sep 6, 2002
Abstract : Architecture bridges the semantic gap between the requirements and software. Application software systems must be architected in order to deal with the current and future needs of the business organization. Managing software projects using architecture-centered methodologies must be an intentional step in the process of deploying information systems ― not an accidental by-product of the software acquisition and integration process.
|
| 7. |
Architecture-Centered Information Systems In The Manufacturing Domain - Part I - Introduction to Software Architecture ( Pages)
by Glen B. Alleman
Sep 4, 2002
Abstract : Architecture bridges the semantic gap between the requirements and software. Application software systems must be architected in order to deal with the current and future needs of the business organization. Managing software projects using architecture-centered methodologies must be an intentional step in the process of deploying information systems ― not an accidental by-product of the software acquisition and integration process.
|
| 8. |
Architecture-Centered Information Systems In The Manufacturing Domain - Part V - Applying the Methodology ( Pages)
by Glen B. Alleman
Sep 19, 2002
Abstract : Architecture bridges the semantic gap between the requirements and software. Application software systems must be architected in order to deal with the current and future needs of the business organization. Managing software projects using architecture-centered methodologies must be an intentional step in the process of deploying information systems - not an accidental by-product of the software acquisition and integration process.
|
| 9. |
Architecture-Centered Information Systems In The Manufacturing Domain - Part IV - Moving From Planning to Implementation ( Pages)
by Glen B. Alleman
Sep 13, 2002
Abstract : Architecture bridges the semantic gap between the requirements and software. Application software systems must be architected in order to deal with the current and future needs of the business organization. Managing software projects using architecture-centered methodologies must be an intentional step in the process of deploying information systems - not an accidental by-product of the software acquisition and integration process.
|
CART 
